Phase 1, Step 5: Upfront Considerations

The transition from legacy baseband to an IP fabric means that "Upfront Considerations" are no longer just about calculating rack units, total BNC counts, and single-point patch bay topologies. In an ST 2110 environment, the physical footprint is highly compressed, but the logical and contractual footprint expands exponentially.

To secure meaningful client sign-off during this phase, the engineering foundation must capture how virtualized routing, software compliance, and deterministic network timing alter classic deployment workflows.

The Paradigm Shift: Baseband vs. ST 2110

Design Area	Legacy Baseband Approach	ST 2110 IP Bridge Reality
System Boundary Definition	Defined by physical I/O ports on a distribution amplifier or routing matrix. Hardware limits are rigid and visually obvious.	Defined by network switch bandwidth, subscription limits, and software edge-device packaging. System capacity is logical rather than physical.
Interoperability & Verification	Passing a signal means checking physical voltages, cable equalization, and clean BNC terminations.	Passing a stream requires control-plane discovery compliance (NMOS IS-04/IS-05) and strict traffic shaping adherence (ST 2110-21).
Timing Architecture	Standard analog Genlock (Black Burst or Tri-Level Sync) distributed via dedicated coaxial overlay networks.	Precision Time Protocol (SMPTE ST 2059-2) running directly over the media network, requiring careful Grandmaster election and boundary clock design.
Client Sign-off Milestone	Client approves physical layout drawings, room dimensions, and functional signal flow blocks.	Client must approve the Multicast Address Plan, network topology models, and explicit software functionality boundaries.

Core Engineering Anchors for Client Sign-Off

To lock down the system design foundation and move past the conceptual phase, four critical pillars must be clearly defined, documented, and presented to the client for structural sign-off:

Network Fabric Topology Model: Establishing whether the facility utilizes a Monolithic Core or a distributed Leaf-Spine Architecture. The client must sign off on the bandwidth allocation (e.g., 25G, 100G, 400G links) and the physical placement of edge switches relative to centralized compute resources.
The Virtual Patch Bay (Multicast Allocation Matrix): Replacing the traditional physical patch layout with a structured, comprehensive Multicast Address Plan. This document assigns deterministic IP ranges to video (ST 2110-20), audio (ST 2110-30), and metadata (ST 2110-40) streams, ensuring zero addressing collisions across the fabric.
PTP Timing Topology and Boundary Mapping: A complete blueprint of the PTP domain tree, specifying primary and secondary Grandmaster clocks, GNSS antenna access points, and switch-by-switch Boundary Clock configurations to prevent timing loops or clock-steer degradation.
Control Plane Boundaries: Explicitly defining how third-party broadcast control systems interact with media nodes via native APIs or open standards like NMOS. This eliminates the "plug and play" myth by establishing exact registry verification milestones before hardware arrives on-site.